Release 10.1A: OpenEdge Development:
Progress Dynamics Repository Reference

gsm_token table — gsmto

This table contains the definitions of security tokens.

Table 11–11 lists the table’s FLA, fields, and foreign keys.

Table 11–11: gsm_token table information 

Table FLA	Fields (data type)	Foreign keys
gsmto	token_obj (Decimal) token_code (Character) token_description (Character) disabled (Logical) system_owned (Logical)	None

Table 11–12 gives details of the table’s indexes.

Table 11–12: gsm_token index information 

Index name	Elements	Type
XPKgsm_token	token_obj	Primary Unique
XAK1gsm_token	token_code	Unique
XIE1gsm_token	token_description	Nonunique

Tokens are used in the application to control access to functions the user can perform within a program using tab folder page names and button names.

Tokens can be created for any tab page names or button labels. Do not include shortcut characters and “...” suffixes. The tokens must be added to the gsm_security_structure table to become active. The gsm_security_structure table enables restricting a token for a specific object instance, specific object, specific product module, or generically for everything.

The framework only checks security if a valid, enabled token exists for the button label or tab folder page.

Once a user is allocated tokens, security restrictions are applied. If a folder page or button has access restrictions set up, only users who have been granted access can use it. However, if security control is set to full access by default and a user has no tokens allocated, then that user is assumed to have full access.

Example tokens would be add, delete, modify, view, copy, page 1, and page 2.